Hi Tom

I’m wondering if you could give me some guidance for solving an issue that I have been experiencing with KmotionCNC. So, from time to time I come across with this error during G-code execution, “invalid buffer times in trajectory planner”, and I have tried a couple different things including increasing the look ahead time, reducing feed rate and I have been double checking the G-code to make sure that there are not invalid characters and everything looks fine.

Thanks in advance,

Regards,

Edward.

Hi Edward,

Sorry to hear you are having trouble. It doesn't sound like the problem is reproducible?

What Version of KMotion are you using?

What are your Trajectory Planner Settings?

Please post your Init C Program.

Anything unusual about your GCode? Can you post it?

Can you describe a scenario when it occurs?

Regards

On 8/10/2016 7:17 PM, Eduardo Barocio vbedwuard_25@... [DynoMotion] wrote:

Hi Tom

I’m wondering if you could give me some guidance for solving an issue that I have been experiencing with KmotionCNC. So, from time to time I come across with this error during G-code execution, “invalid buffer times in trajectory planner”, and I have tried a couple different things including increasing the look ahead time, reducing feed rate and I have been double checking the G-code to make sure that there are not invalid characters and everything looks fine.

Thanks in advance,

Regards,

Edward.

Tom,

Yes, the problem it's kind of random. But let me share you the detail of the system. The version is 4.33, trajectory planner settings are Break angle 360 degrees, look ahead 10 sec, collinear tolerance 0.01, corner tolerance 0.035, facet angle 1.2 degrees. I attached the init C program as well as a g-code that gave me this problem. You will notice that the g-code looks all normal, but the error popped up around line 9000 the three times I tried this code. After facing the error I tried to continue the program execution where it left off but it only executed for around 100 more lines and the same error showed up.

I'm suspecting that there is an issue with windows (virus or something else) but I wanted to make sure first that everything is right from the kflop's side.

Thanks again for all your help,